In foreman-installer this was added conditionally if python content type was enabled. I think we should do the same here so as not to expose routes that have no effect.

I've updated the template to conditionally include the /pypi Location block only when pulp_python is in the enabled plugins list.

The problem is that this variable is from the pulp role, and this is the httpd role.

@evgeni -- do you think we should go with role variables httpd_pulp_python or we should have Pulp role require/expect httpd, and use our drop in directory to have the pulp role drop in chunks?

Just checking in on this when you have a moment. Happy to proceed based on your suggestion.

Jinja has an include tag, so we could do something like:

# httpd/defaults/main.yml
httpd_enabled_pulp_snippets: []

# vhost.conf.j2:
{% for httpd_pulp_snippet in httpd_enabled_pulp_snippets %}
{% include httpd_pulp_snippet+'.j2' %}
{% endfor %}

and then feed httpd_enabled_pulp_snippets with the right list of enabled pulp plugins at the foremanctl level (and of course provide those snippets)

Thanks! Implemented using httpd_enabled_pulp_snippets with includes as suggested.

I think here we need to tie this into our features. For example, see

And you can look down at line 32 in this file to see it being referenced.

@evgeni -- did we have an intent to define "meta" features within the features.yaml? e.g. content/* features

Updated to use enabled_features instead of pulp_enabled_plugins and added content/python to the katello flavor, following the same pattern as content/ansible.

so far we have not yet